Skip to content

Add Bulkactions 2026-07-06-preview version#43925

Closed
NneOkeke wants to merge 21 commits into
Azure:mainfrom
NneOkeke:bulkactions-20260606-preview-version
Closed

Add Bulkactions 2026-07-06-preview version#43925
NneOkeke wants to merge 21 commits into
Azure:mainfrom
NneOkeke:bulkactions-20260606-preview-version

Conversation

@NneOkeke

Copy link
Copy Markdown
Member

ARM (Control Plane) API Specification Update Pull Request

Tip

Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

spec_pr_review_workflow_diagram

Purpose of this PR

What's the purpose of this PR? Check the specific option that applies. This is mandatory!

  • New resource provider.
  • New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
  • Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
  • Update existing version to fix OpenAPI spec quality issues in S360.
  • Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
  • Other, please clarify:
    • edit this with your clarification

Due diligence checklist

To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

  • I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
  • I have reviewed following Resource Provider guidelines, including
    ARM resource provider contract and
    REST guidelines (estimated time: 4 hours).
    I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
  • A release plan has been created. If not, please create one as it will help guide you through the REST API and SDK creation process.

Additional information

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

  • First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
  • If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
  • To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
  • For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
    and https://aka.ms/ci-fix.
  • For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
  • If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
    This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
  • If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.
  • For guidance on SDK breaking change review, refer to https://aka.ms/ci-fix.

@github-actions

github-actions Bot commented Jun 11, 2026

Copy link
Copy Markdown

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ This PR is in purview of the ARM review (label: ARMReview). This PR must get ARMSignedOff label from an ARM reviewer.
    This PR is not ready for ARM review (label: NotReadyForARMReview). This PR will not be reviewed by ARM until relevant problems are fixed. Consult the rest of this Next Steps to Merge comment for details.
    Once the blocking problems are addressed, add to the PR a comment with contents /azp run. Automation will re-evaluate this PR and if everything looks good, it will add WaitForARMFeedback label which will put this PR on the ARM review queue.
    For details of the ARM review, see aka.ms/azsdk/pr-arm-review
  • ❌ This PR is NotReadyForARMReview because it has the BreakingChangeReviewRequired label.
  • ❌ This PR has at least one breaking change (label: BreakingChangeReviewRequired).
    To unblock this PR, follow the process at aka.ms/brch.
  • ❌ The required check named TypeSpec Validation has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide


Comment generated by summarize-checks workflow run.

@github-actions github-actions Bot added ARMReview new-api-version resource-manager TypeSpec Authored with TypeSpec WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Jun 11, 2026
@github-actions

github-actions Bot commented Jun 11, 2026

Copy link
Copy Markdown

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language API Review for Package
Swagger Microsoft.Compute-Bulkactions
TypeSpec Microsoft.Compute
Go sdk/resourcemanager/compute/armbulkactions
Python azure-mgmt-computebulkactions
Java com.azure.resourcemanager:azure-resourcemanager-compute-bulkactions
JavaScript @azure/arm-compute-bulkactions

Comment generated by After APIView workflow run.

@sandipsh

Copy link
Copy Markdown
Contributor

ARM review update for latest iteration (head: e0b058b):

  • No prior ARM review threads/comments were present on this PR, so there were no old threads to resolve/reply.
  • Posted new blocking inline comments for ModelValidation INVALID_FORMAT regressions in 2026-06-06-preview examples.

Validation status checked for this changeset:

  • Swagger SemanticValidation: success
  • TypeSpec Validation: success
  • Swagger ModelValidation: failing (multiple INVALID_FORMAT errors in changed examples)
  • Swagger LintDiff: failing (SpecModelError: .../preview/2026-06-06-preview/Bulkactions.json not found in specModel)
  • Swagger Avocado: failing with actionable errors (not MULTIPLE_API_VERSIONS):
    • UNREFERENCED_JSON_FILE for preview/2026-06-06-preview/Bulkactions.json
    • NOT_LATEST_API_VERSION_IN_DEFAULT_TAG for default tag configuration

Action required:

  • Update specification/compute/resource-manager/Microsoft.Compute/Bulkactions/readme.md to include preview/2026-06-06-preview/Bulkactions.json and ensure default tag points to latest API version.
  • Fix invalid UUID and ARM-ID sample values in the new 2026-06-06-preview examples.

@sandipsh sandipsh added ARMChangesRequested and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Jun 11, 2026
@github-actions github-actions Bot added ARMAutoSignedOff-IncrementalTSP ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed ARMChangesRequested labels Jun 12, 2026
@NneOkeke NneOkeke added the PublishToCustomers Acknowledgement the changes will be published to Azure customers. label Jun 12, 2026
2) Added suppression for record<unknown> in baseProfile and resourceOverrides of ResourceProvisionPayload
operationId: string;

@doc("Unique identifier for the resource involved in the operation, for example Azure resource ID")
resourceId?: armResourceIdentifier;

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is an unversioned change. Is this a correction, or is this meant to be in the new version only?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

only the doc only unversioned changes are allowed in the previous versions, will update this.

@doc("High level response from an operation on a resource")
model ResourceOperation {
@doc("Unique identifier for the resource involved in the operation, for example Azure resource ID")
resourceId?: armResourceIdentifier;

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another unversioned change

description: string;

@doc("The type of resources used in the start request eg virtual machines")
@doc("The type of resources used in the request eg virtual machines")

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

doc-only unversioned change (generally acceptable)

@doc("The type of resources used in the deallocate request eg virtual machines")
type: string;
@doc("The execute-type request for power operations")
model ExecuteTypeRequest {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this is only used as a mix-in (i.e ...ExecuteTypeRequest in other models) then this should be an alias, to prevent it from appearing in other api-versions

@doc("The response from a start request")
model StartResourceOperationResponse {
@doc("Common model for operation response")
model OperationResponse {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this is only used to mix in to other model types, you should model this as an alias. This will porevent the type showing up in previous versions.

Sumedh Sandeep Parvatikar and others added 3 commits June 18, 2026 15:02
…sallow breaking change from the previous preview version.
1) Added loosely typed json for baseProfile and resourceOverrides
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ARMReview BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required Compute new-api-version NotReadyForARMReview PublishToCustomers Acknowledgement the changes will be published to Azure customers. resource-manager TypeSpec Authored with TypeSpec

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants